bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Sun, 14 Jun 2026 08:12:01 +0000 (10:12 +0200)
committerSylvestre Ledru <sylvestre@debian.org>
Sun, 14 Jun 2026 08:12:01 +0000 (10:12 +0200)
commitefc68e202841358b5a9fe9fe0d0ab4229a6b892f
treed2f6e37d0aad969d869825601c44423ce21f6ca3
parentd188e85d362381a8f92164f4ac71abb5f476db12
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h